Over night I have been thinking about how this blue flag penalty could be implemented, but it doesn't seem to be a straight forward thing.
When a player is slow for a reason (skills, technical issue on the car, been in an accident, etc.) the whole field will lap him/her at some point. That means a lot of blue flags will be given, but only counting them isn't doing justice to the player that gets them. I mean, maybe he/she moves out of the way ASAP but since then the next car will appear, the flag count will go up and up. A way to go around that is to count the number of flags within a given time period, but then again, when all the cars are catching up, it still might be too many flags within X seconds.
As far as I know, Lapper can't indicate which players causes you to get a blue flag. It would help to be able to know that Player A gets a blue flag because of Player B and if those are too many, you could apply a penalty. Then the counting starts again when Player A gets a blue flag because of Player C.
I have no idea if there's an Insim packet to get that information and if so, if Bass-Driver would be willing to implement it.
/p_30 USERNAME :give 30 second time penalty
/p_45 USERNAME :give 45 second time penalty
/p_dt USERNAME :give drive through penalty
/p_sg USERNAME :give stop-go penalty
The flags are found in lfslapper.lpr (I have version 7.0.4.10 , which isn't the latest version but in a higher version it is as well), see this:
######################################################################################### #Action on Event when player receives a Flag (Yellow/Blue flags and Lag/Missing packets)# ######################################################################################### # The Flags below returns 1 or 0 depends on which flag is received by the user #$YellowFlag: Player receives a YellowFlag #$BlueFlag : Player recieves a BlueFlag #$LagFlag : Player is lagging or is missing carpackets #$Time : ShortTimeFormat,same as GetLapperVar("ShortTime");
$PlayerFlagEvent = -1; #Enable Event 1 = ON / -1 = OFF Event OnPlayerFlags($userName,$YellowFlag,$BlueFlag,$LagFlag,$Time) # Player event /* IF( $YellowFlag == 1) THEN privmsg("^3YELLOW FLAG"); ENDIF IF( $BlueFlag == 1) THEN privmsg("^4BLUE FLAG"); ENDIF IF( $LagFlag == 1) THEN privmsg("^5LAG"); ENDIF */ EndEvent
This /* and this */ means that the code between those two signs is disabled.
Remove both of them and the code will be active on the next reload of Lapper, that can be done by typing this into the LFS chat (if you have admin rights on Lapper, that is): !reload
To get rid of "LAPPERSCRIP DEVELOPEMENT" search for this piece of code in lfslapper.lpr:
################################################# #Connect messages when a player joins the server# #################################################
Version 7.0.6.4 never made it to a public version (please correct me if I am wrong Bass-Driver) and must be considered a beta version.
If you are on 7.0.6.3 you are on the latest released version and should be able to do all you want to, including the flags we were talking about earlier in this thread.
This will send data from Lapper to the mentioned PHP file on a webserver.
Retrieving the data by the PHP-file looks like this:
<?php ### Get data send through LFS Lapper ### $servername= $_GET['servername']; $race_date= $_GET['date']; $password= $_GET['password']; ### End ### ?>
Then you can do what ever you want with it.
In return you can make PHP do something in Lapper as well, see this example:
<?php echo "cmdLFS(\"/msg ^1WARNING: ^7You are using a proxy!\");"; ?>
This will send a message within Lapper, but you can also make buttons popup or be closed or what ever you like.
The possibilities are nearly endless.
There is no studio working on LFS. It's a project of Scawen (as coder)and Eric (graphics designer) and that's it. They don't use any known software to build this game, as Scawen has build all on its own. Money isn't what drives them, perfection is and they do a fine job with that. LFS has come a long way since I first discovered it and I am sure it will go a long way as well. All that's going on behind the scenes now, will be huge step forward while quality is still remained. Either people like this slow progress and value the game for what it is already (a masterpiece) or they don't like it and move along.
Aha, I had that issue too a long time ago on my VPS.
I needed to install something from Microsoft.
Quickly searched through my Hotmail, but the answer wasn't in there.
Need to search my private email (or check my VPS) when I am home again.
To be continued.
Scawen has already said that he worked on the AI during the tyre physics update (which still isn't finished) and that the improved AI will appear in the game once tyre and graphical update will be ready for testing.
As far as I know, Lapper doesn't show split times in the topbar by default.
You might want to check the file named "addonsused.lpr" as that's the one the enables\disables modules that are loaded when Lapper is started (or restarted using command: !reload).
I have loaded your script and found several errors:
This: privmsg($userName,"you successfully entered the Track with Pinto powered XRT!);
Should be: privmsg($userName,"you successfully entered the Track with Pinto powered XRT!");
This: privmsg($userName,"you successfully entered the Track with Zetec powered XRT!);
Should be: privmsg($userName,"you successfully entered the Track with Zetec powered XRT!");
This: Sub tws_Zetec( $KeyFlags )
Should be: Sub tws_Zetec( $KeyFlags , $id )
This: Sub tws_Pinto( $KeyFlags )
Should be: Sub tws_Pinto( $KeyFlags , $id )
All these errors were visable in the log file:
3/23/2020 8:17:11 PM -> Error: Unclosed string on file: ".\AB-configs\.\..\includes\.\test\test_restrict.lpr" at line #41
3/23/2020 8:28:48 PM -> Syntax error: Incorrect number of arguments at line #76 in function 'tws_pinto' script aborted
You might have looked at the wrong lof file, as Lapper has two of them.
This file* is the correct file to check: 127.0.0.1-29994-ERR.log
*29994 = the port number your Lapper is running on, so that might differ on your end
Of course it's always a good thing to learn the coding skills your self and you are well on your way, but if you want some inspiration or to have a fully developed handicap (or restrictions as you call it) system, have a look at the script I made in the past: https://www.lfs.net/forum/post/1954184#post1954184
Add a debugging message in both Subs and see if the tekst appears when the button is clicked.
If so, there's a problem within the Sub(s) and if not, there is a problem with the button.